Configuring Task Runner to Automate ETL Imports and Exports

You can configure Task Runner to run ETL processes unattended at a scheduled time (for example, after business hours, when the data-processing load is at a minimum). Using pre-programmed step templates, Task Runner initiates ETL as a background process to extract data from foreign-database import files, map the data to Voyager codes and accounts, transform the data into Voyager data format, and insert the data into a Voyager database. You can also schedule data-export activities.

Prior to setting up Task Runner tasks and schedules, manually import some data samples to find and correct any problems in the import-data files, foreign database options, ETL-group data objects, and mapping configuration.

You can use the APPTASK template to automate ETL scheduling. ETL processes run on the same server as Task Runner (typically, a dedicated report server).

The APPTASK template uses the following four ETL operations:

l	ImportCSVDir Imports .csv files.

l	ImportXMLDir Imports .xml files.

l	ExportCSVDir Exports .csv files.

l	ExportXMLDir Exports .xml files.

To configure Task Runner using the APPTASK step template

1	From the Voyager System Administration side menu, Select Admin > Task Runner > Task > Add. The Task Runner Task screen appears.

2	Complete the screen with a unique code and name for the task. (The Code field has a 12-character limit.)

3	Click Save. The Name/Value table appears.

4	Click the Steps button . The Task Runner Step screen appears.

5	Complete the screen. For more information, see “Task Runner Step Screen Reference -- APPTASK”.

6	Click Save.

Task Runner Step Screen Reference -- APPTASK

l Top Part of Screen

Template	The APPTASK step template. The Name and Value columns appear at the bottom of the screen.
Order	The order that you want this step to execute within the task.
Inactive	Skips this step within the task.
Execute only if task already failed	Executes this step, even if the main task has failed.

l Name/Value Table

ClassName	YSI.ETL.AppTask.dll#YSI.ETL.AppTask.TaskClasses.ETLoperation where the ETLoperation string represents one of four classes, as follows: ysiImportCSVDir Imports .csv files. ysiImportXMLDir Imports .xml files. ysiExportCSVDir Exports .csv files. ysiExportXMLDir Exports .xml files. For example, if you are configuring Task Runner to automatically import a .csv file, the ClassName would be YSI.ETL.AppTask.dll#YSI.ETL.AppTask.TaskClasses.ysiImportCSVDir (inclusive of all symbols and punctuation).
Database, Password, Platform, Server, User	Server name and logon parameters for the database that ETL uses for importing and exporting data.
URL	Type &ForeignDB=foreign database name. Substitute the name of the foreign database that you are using (for example, &ForeignDB=ETLimport).

To add Task Runner schedules for ETL processes

You can schedule ETL-import and export process to run at any time, on either a one-time or recurring basis.

For more information about scheduling these tasks, see the “Task Runner” chapter in the Yardi Service Manager Installation and Setup Guide.